Skip to content

fix(client): startWorkflow throws on 200 response with an empty body - #173

Open
mp-orkes wants to merge 1 commit into
mainfrom
fix/empty-response-body-raises
Open

mp-orkes wants to merge 1 commit into
mainfrom
fix/empty-response-body-raises

Conversation

@mp-orkes

@mp-orkes mp-orkes commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Problem

During safety testing, with infrastructure being killed (on purpose), the server answered startWorkflow with HTTP 200 and an empty body once in ~150k request. The workflow was not created.

The client returned null for that. A null id is an error.

Change

startWorkflow now throws a ConductorClientException when the response has no workflow id.

@mp-orkes
mp-orkes force-pushed the fix/empty-response-body-raises branch 4 times, most recently from 9b13944 to 1bb8bce Compare September 23, 2026 15:37
A successful response carrying no workflow id came back as a null return
value, so a caller saw a successful start with no id and no way to find the
execution. It now raises instead. Scoped to startWorkflow; deserialization is
unchanged for every other endpoint.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mp-orkes
mp-orkes force-pushed the fix/empty-response-body-raises branch from 1bb8bce to 758c8d8 Compare September 23, 2026 15:43
@mp-orkes
mp-orkes marked this pull request as ready for review September 23, 2026 15:48
@mp-orkes mp-orkes changed the title fix(client): raise on a successful response with an empty body fix(client): startWorkflow on a successful response with an empty body Sep 23, 2026
@mp-orkes mp-orkes changed the title fix(client): startWorkflow on a successful response with an empty body fix(client): startWorkflow throws on 200 response with an empty body Sep 23, 2026
@mp-orkes mp-orkes self-assigned this Sep 23, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant